Great job! 💪
So far, we've discussed and agreed not to incorporate dotenv support. Instead, we'll provide documentation on how to implement it as a best practice. This way, users have the flexibility to configure their environment as they see fit.

Great job! 💪 So far, we've discussed and agreed not to incorporate dotenv support. Instead, we'll provide documentation on how to implement it as a best practice. This way, users have the flexibility to configure their environment as they see fit.

Ah ok. My ticket said I should implement this, or at least I understood it that way 😉

I would like to install the dotenv-dependency anyway and prepare the .env-file for the user upon npm askui init. The user only has to add the correct import in askui-helper.ts for the best practice to work. Is that ok from your side @mlikasam-askui ?

Great job! 💪 So far, we've discussed and agreed not to incorporate dotenv support. Instead, we'll provide documentation on how to implement it as a best practice. This way, users have the flexibility to configure their environment as they see fit.

Ah ok. My ticket said I should implement this, or at least I understood it that way 😉

I would like to install the dotenv-dependency anyway and prepare the .env-file for the user upon npm askui init. The user only has to add the correct import in askui-helper.ts for the best practice to work. Is that ok from your side @mlikasam-askui ?

Personally, I don't like shipping it like that. However, I would advise waiting for @programminx-askui. You can discuss it with him, and he can then bring it up with @dom-askui. I can't decide for the team.

Moved the docs part to askui/askui-dev-docs#10